Repository navigation
fix(10.x.x): SYNC_EXHAUSTION stops dispatching after a DataLoader cache hit on a completed future. - #2215
Merged
samuelAndalon merged 1 commit intoOct 5, 2026
Conversation
…he hit on a completed future.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📝 Description
With
SYNC_EXHAUSTION, aDataLoader.load()that hits the cache on an already completed future drivesonDispatchAllLoadCounterto-1. That stops all further dispatching for the request, so later loads never complete and the operation hangs.Each load is now decremented from the counter it was added to.
takeSnapshot()swaps counter instances, and the dispatcher keeps a per-load context. The old public tracking methods are deprecated; there are no API or binary changes.🔗 Related Issues
Counter-based dispatch state introduced in #2106.